Method and system for offering a credit product by a credit issuer to a consumer at a point-of-sale

ABSTRACT

A method for offering at least one credit product by at least one credit issuer to a consumer at a point-of-sale between a merchant and the consumer. The method includes the steps of: providing a credit issuer data set including a plurality of data fields to a central database; initiating a transaction between the consumer and the merchant at the point-of-sale; offering, to the consumer at the point-of-sale, the at least one credit product; and presenting, to the consumer at the point-of-sale, at least one data field in the credit issuer data set. The at least one data field presented to the consumer is populated with data directed to the credit product, the credit issuer, or any combination thereof. An apparatus and system are also disclosed.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 16/112,301, filed Aug. 4, 2018, which is a continuation of U.S. application Seri. No. 15,628,090, filed on Jun. 20, 2017 (issued as U.S. Pat. No. 10,068,289 on Sep. 4, 2018, which is a continuation of U.S. application Ser. No. 15/231,203, filed on Aug. 8, 2016 (issued as U.S. Pat. No. 9,684,931 on Jun. 20, 2017), which is a continuation of U.S. application Ser. No. 14/245,964, filed Apr. 4, 2014 (issued as U.S. Pat. No. 9,412,132 on Aug. 9, 2016), which is a continuation of U.S. application Ser. No. 14/047,791, filed Oct. 7, 2013, (issued as U.S. Pat. No. 8,719,159 on May 6, 2014), which is a continuation of U.S. application Ser. No. 11/651,141, filed Jan. 9, 2007, (issued as U.S. Pat. No. 8,554,669 on Oct. 8, 2013), all of which are incorporated herein by reference in their entirety.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention is related generally to credit systems and consumer/credit issuer relationships and consumer/merchant relationships, and in particular, to a method and system for offering a credit product by a credit issuer to a consumer at a point-of-sale, such as in a person-to-person environment, online environment, etc.

Description of Related Art

In order to enable convenient purchases of goods and services by consumers, the financial service industry has developed many alternative payment methods that allow a consumer to engage in a transaction and receive goods and services on credit. For example, such alternative payment methods may include checks, ATM or debit cards, credit cards, charge cards, etc. Prior to the birth of virtual commerce, as discussed below, such payment options provided adequate convenience and transactional security to consumers and merchants in the marketplace. Virtual commerce and the growth of the Internet as a medium for commerce have placed pressure on the payment options discussed above on both the convenience and transactional security and profitability by the credit issuer. Currently, available payment options include significant shortcomings when applied to remote purchasers, such as purchases where the buyer and the seller (that is, the merchant) are not physically proximate during the transaction. Specific examples of remote purchases are mail order, telephone order, the Internet and wireless purchases.

In many situations, such as at a typical point-of-sale (POS), and during the transaction, the consumer may wish to obtain some credit product. For example, during an online transaction at a merchant's site, the consumer may wish to obtain a credit product, such as a standard credit card account, an online credit account or some other similar credit vehicle. In addition, the consumer may wish to obtain that credit product for use in the transaction that he or she is currently engaged in with the merchant.

According to the prior art, in such a situation, the consumer applies for the credit card at the home page or some other page of the merchant's site. In some instances the consumer may be responding to some displayed offer of credit issuer on the merchant-affiliated website. For example, the merchant may offer a discount, e.g., 10% discount on all purchases, if the consumer obtains that specific credit product. If the consumer does indeed select the option to apply for that credit product, he or she is directed or re-routed from the merchant's site to the credit issuer website. Such a situation is tenuous for the merchant, since it is never preferable for a potential purchaser to leave the website. In such a situation, if the consumer is displeased with the credit product application process, he or she may simply terminate the entire transaction and find another merchant site. Further, during the application process at the credit issuer website, various technical “glitches” may arise, causing the consumer to be disconnected from the site, misdirected from the credit issuer site, “knocked” offline, etc., all of which is a result of the movement from the merchant site to the credit issuer site.

One reason that the merchant must allow the consumer to be redirected to the credit issuer site is the merchant's lack of pertinent information and data regarding the credit product. For example, the merchant could not provide the appropriate terms and conditions of the credit product, nor the required Credit Member Agreement, both of which must, by law, be presented to the consumer (and acknowledged by the consumer) before establishing the credit account. Instead, this information is presented to the consumer at the credit issuer site, e.g., at the credit issuer application page, since the credit issuer desires to maintain absolute control over this important and dynamic data. The credit issuer may believe that the merchant will not display the information in the required format, will not update the information in a timely, complete and accurate manner, will not obtain the required acknowledgements, etc.

Another drawback to the prior art is the duplicative information required from the consumer during both the transaction and the credit application process. Since the consumer is directed from the merchant's site to the credit issuer's application page, many different data fields will require entry at both sites, again causing a less-than-desirable online experience by the consumer. For example, during the transaction, the consumer may have already supplied to the merchant his or her name, address, telephone number, e-mail, billing address, ship-to address, etc. Then, during the credit application phase on the credit issuer's site, the consumer must again enter all of this information, since the merchant site and the credit issuer site are separate. This represents a deficiency in the consumer/merchant/credit issuer relationship.

SUMMARY OF THE INVENTION

Therefore, it is an object of the present invention to provide a method and system for offering a credit product by a credit issuer to a consumer at a point-of-sale that overcomes the drawbacks and deficiencies of the prior art. It is another object of the present invention to provide a method and system for offering a credit product by a credit issuer to a consumer at a point-of-sale that maximizes the consumer online experience. It is yet another object of the present invention to provide a method and system for offering a credit product by a credit issuer to a consumer at a point-of-sale that ensures that the most timely, complete and accurate credit product information is presented to the consumer. It is a still further object of the present invention to provide a method and system for offering a credit product by a credit issuer to a consumer at a point-of-sale that ensures that the appropriate acknowledgements and consumer interactions are obtained. It is a further object of the present invention to provide a method and system for offering a credit product by a credit issuer to a consumer at a point-of-sale that allows the credit issuer to maintain control over the credit product data, while allowing the merchant to retain the consumer interaction. It is a still further object of the present invention to provide a method and system for offering a credit product by a credit issuer to a consumer at a point-of-sale that allows for the pre-population of certain consumer data in the credit application phase of a consumer/credit issuer transaction.

The present invention is directed to a method for offering at least one credit product by at least one credit issuer to a consumer at a point-of-sale between a merchant and the consumer. The method includes the steps of: providing a credit issuer data set including a plurality of data fields to a central database; initiating a transaction between the consumer and the merchant at the point-of-sale; offering, to the consumer at the point-of-sale, the at least one credit product; and presenting, to the consumer at the point-of-sale, at least one data field in the credit issuer data set. The at least one data field presented to the consumer is populated with data directed to the credit product.

The present invention is further directed to an apparatus for offering at least one credit product by at least one credit issuer to a consumer at a point-of-sale between a merchant and the consumer. The apparatus includes: means for providing a credit issuer data set including a plurality of data fields to a central database; means for initiating a transaction between the consumer and the merchant at the point-of-sale; means for offering, to the consumer at the point-of-sale, the at least one credit product; and means for presenting, to the consumer at the point-of-sale, at least one data field in the credit issuer data set. At least one data field presented to the consumer is populated with data directed to the credit product.

The present invention is also directed to a system for offering at least one credit product by at least one credit issuer to a consumer at a point-of-sale between a merchant and the consumer. The system includes a storage mechanism including a central database and at least one input mechanism for transmitting, to the storage mechanism: (i) a credit issuer data set having a plurality of data fields therein; (ii) a request, from the merchant, for at least one data field of the credit issuer data set to be transmitted, or any combination thereof. A processor mechanism processes data input, data requests, data manipulation, data transmission, or any combination thereof, and a communication mechanism is used for transmitting, to the merchant, at least one data field in the central database responsive to the request. Finally, a merchant output mechanism presents, to the consumer at the point-of-sale, the least one data field transmitted from the communication mechanism. At least one data field is populated with data directed to the credit product.

These and other features and characteristics of the present invention, as well as the methods of operation and functions of the related elements of structures and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. As used in the specification and the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWING(S)

FIG. 1 is a schematic view of one embodiment of a method and system for offering at least one credit product by at least one credit issuer to a consumer at a point-of-sale according to the present invention;

FIG. 2 is a schematic view and illustrative screenshots of another embodiment of a method and system for offering at least one credit product by at least one credit issuer to a consumer at a point-of-sale according to the present invention;

FIG. 3 is a schematic view and illustrative screenshots of a further embodiment of a method and system for offering at least one credit product by at least one credit issuer to a consumer at a point-of-sale according to the present invention;

FIG. 4 is a schematic view and flow diagram of another embodiment of a method and system for offering at least one credit product by at least one credit issuer to a consumer at a point-of-sale according to the present invention;

FIG. 5 is a schematic view of yet another embodiment of a method and system for offering at least one credit product by at least one credit issuer to a consumer at a point-of-sale according to the present invention; and

FIG. 6 is a schematic view of a system for offering at least one credit product by at least one credit issuer to a consumer at a point-of-sale according to the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

It is to be understood that the invention may assume various alternative variations and step sequences, except where expressly specified to the contrary. It is also to be understood that the specific devices and processes illustrated in the attached drawings, and described in the following specification, are simply exemplary embodiments of the invention.

The present invention is directed to a method and system 10 for use in offering at least one credit product 12 by one or more credit issuers 14 to a consumer 16. In particular, the method and system 10 implement this offer at a point-of-sale between a merchant 18 and the consumer 16. Further, the presently-invented method and system 10 are useful in connection with a variety of credit products, such as credit cards, online credit accounts, debit cards, and other similar credit vehicles. In addition, the method and system 10 of the present invention can be used in connection with a variety and any quantity of credit issuers 14, consumers 16 and merchants 18.

In particular, the present invention provides a credit issuer data set 20 to a central database 22. The credit issuer data set 20 includes multiple data fields 24. Next, a transaction is initiated between the consumer 16 and the merchant 18 at the point-of-sale. One or more credit products 12 are offered to the consumer 16 at the point-of-sale. Finally, one or more data fields 24 in the credit issuer data set 20 are presented to the consumer 16 at the point-of-sale. These data fields 24, which are presented to the consumer 16, are populated with data directed to the credit product 12 and/or the credit issuer 14.

The data fields 24 presented to the consumer 16 at the point-of-sale may be populated with a variety of data and information. For example, these data fields 24 may comprise terms relating to the credit product 12, conditions relating to the credit product 12, card member agreement data, credit product offer data, credit issuer data, application data, etc. Accordingly, during the offering step and/or the presenting step, multiple data fields 24 from the credit issuer data set 20 are provided to the consumer 16 during the transaction at the point-of-sale. In one preferred form, the multiple data fields 24 are populated with data reflecting terms and conditions relating to the credit product 12, as well as a card member agreement data form.

By providing certain data fields 24 to the consumer 16 at the point-of-sale, the consumer 16 does not need to directly access the credit issuer 14 in order to obtain the credit product 12. Instead, the information and data is either provided to or through the merchant 18 to the consumer 16 at the point-of-sale. This alleviates the need for any direct communication, access or movement to the credit issuer 14. In addition, the presently-invented system 10 provides the merchant 18 with the unique advantage of maintaining and retaining the consumer 16 at the point-of-sale at all times during the transaction, as well as during any credit transaction or credit product 12 presentation, application and consummation between the consumer 16 and the credit issuer 14.

In one preferred and non-limiting embodiment, and as illustrated in schematic form in FIG. 1, the present method and system 10 is useful in connection with an electronic transaction between the consumer 16 and the merchant 18. Accordingly, the point-of-sale would be an online location of the merchant 18, such as a website, web page or other online location. In this embodiment, the offering step and/or the presenting step may include displaying a web page, an electronic document, a window, a popup window, etc., which displays the data fields 24 to the consumer 16.

As seen in FIG. 1, the consumer 16 accesses the merchant's 18 online location through a computing device 26, such as a personal computer, a laptop, a PDA, a cellular phone, an electronic device or other means of communication. Accordingly, some time during the transaction process between the merchant 18 and the consumer 16, the consumer 16 encounters or utilizes an interactive interface 28, which allows information, such as the data fields 24, to be presented to the consumer 16, as well as allows for various consumer 16 input to the system 10.

In the embodiment of FIG. 1, the merchant 18 provides the credit issuer data set 20 and/or various data fields 24 from the data set 20 to the consumer 16 via the interactive interface 28, as well as over a network N. In this manner, since the merchant 18 has the credit issuer data set 20 available for offer and presentation to the consumer 16, the consumer 16 does not need to be redirected to the credit issuer 14, such as the credit issuer 14 site online.

It is envisioned that the central database 22 be either maintained at the merchant 18 location or site, however, more preferably at a central system 30 site, which is accessible by and/or in communication with the merchant 18. While, as discussed above, the central database 22 may be stored locally on the merchant 18 site, this may give rise to various security concerns on both the credit issuer 14 side as well as the merchant 18 side. For example, the merchant 18 may not desire to have some updateable and dynamic central database 22 accessible by third parties on their site. On the credit issuer 14 side, the credit issuer 14 may not desire to have the merchant 18 in control of the credit issuer data set 20, as well as the data fields 24 therein. Therefore, it appears preferable to have the central database 22 located at some central and accessible system 30.

Also as seen in FIG. 1, multiple credit issuers 14 may provide their individualized and unique credit issuer data set 20 and data fields 24 to either the central system 30 for entry into the central database 22, or directly into the central database 22. The credit issuer 14 will be in communication with the central system 30 and/or central database 22 through secure systems, online systems, wireless systems, over the network N, etc. However, such an arrangement demonstrates the ability of the credit issuer 14 to access their own information and data fields 24, and provide the updated credit issuer data set 20 to the central database 22 for release to the merchant 18 and eventually the consumer 16. Accordingly, this ensures that the data fields 24 and credit issuer data set 20 are timely, accurate and comply with applicable regulations regarding the credit issuers 14 and merchants 18.

With respect to the interactive interface 28, which is shown in various forms in FIGS. 2 and 3, this interactive interface 28 is in communication with the central database 22, which is located at the merchant site 18 or at the central system 30. Further, this interactive interface 22 is programmed or configured to display the data fields 24, which are populated with data reflecting the credit product 12 offer data 32, to the consumer 16. Further, the interface 28 allows for or accepts consumer 16 input data 34.

Accordingly, as seen in the illustrative screen shots of FIG. 2, some offer data 32 may be presented to the consumer 16 during the transaction, such as an indication that the consumer 16 is eligible for a specific credit product 12 or multiple credit products 12. In this case, the consumer input data 34 would be some response to this offer data 32, such as whether the consumer 16 is interested or not interested. Next, the interactive interface 28 is in communication with the central database 22 and used for displaying the data fields 24 populated with data reflecting credit product application data 36. Such application data 36 would include the data fields and requests necessary for the consumer 16 to complete an application for the credit product 12 for delivery to the credit issuer 14 via the merchant 18. In addition, the input data 34 from the consumer 16 will also be accepted at this screen or portion of the transaction, and will be responsive to the application data 36 and questions on the application.

Further, as seen in FIG. 2, the interactive interface 28 is in communication with the central database 22 and used to display data fields 24 populated with data reflecting terms and conditions data 38 relating to the credit product 12, and/or card member agreement data 40, also relating to the credit product 12. This terms and conditions data 38 and card member agreement data 40 would be presented or displayed to the consumer 16 after processing of the input data 34 of the consumer 16 related to the application and application data 36 of the credit product 12. In response to this terms and conditions data 38 and card member agreement data 40, the consumer 16 provides additional input data 34, such as an acknowledgment that he or she has read, understood and agrees to the terms and conditions data 38 and card member agreement data 40.

Finally, in one preferred and non-limiting embodiment, result data 42 is presented or provided to the consumer 16. For example, this result data 42 may include some indication of success of the establishment of the credit product 12 account, or even, as shown in FIG. 2, an indication that the credit product 12 has been activated and has been used in connection with the present transaction, thereby completing the transaction. Importantly, all of these consumer 16/merchant 18/credit issuer 14 interactions have occurred directly at the interactive interface 28 and in connection with the merchant 18 website or point-of-sale, without the requirement for communications between the consumer 16 and the credit issuer 14, or a redirect to the credit issuer 14 site.

As discussed above, the interactive interface 28 is in communication with the central database 22, whether the central database 22 is located at the merchant 18 point-of-sale (or site) or the central system 30 location (or site). In addition, the interface 28 is programmed or configured to appropriately format and display various data fields populated with data. For example, such data may include interest rate data, credit limit data, purchase data, charge data, cost data, expense data, annual fee data, interest accrual data, statement data, account data, fund advancement data, transfer data, delinquency data, payment term data, account review data, credit product data, credit issuer data, contract data, liability data, certification data, privacy data, personal information use data, collected information data, consent data, foreign data, access data, online service data, phone service data, liability data, representation data, warranty data, termination data, indemnity data, term variation data, communication data, assignment data, rights data, governing law data, or any combination thereof.

In another embodiment, and as discussed above, the interface 28 is in communication with the central system 30, such as a consumer processing system, which either is in communication with or acts as the repository for the central database 22. Further, other than merely housing the central database 22, the central system 30 may have additional functionality. For example, the central system 30 may be programmed or configured to authenticate the consumer 16, verify the consumer 16, approve or deny a consumer 16 application (based upon the consumer input data 34), verify the transaction, process consumer 16 data, process merchant 18 data, process credit issuer 14 data, process transaction data and/or process credit product 12 data. Accordingly, the central system 30 may be capable of engaging in the various verification, authentication and similar functions with respect to the consumers 16, merchants 18 and credit issuers 14.

As discussed above, the consumer input data 34 may be provided by the consumer 16 to the central system 30, central database 22, merchant 18 and/or credit issuer 14 as responsive to offer data 32, application data 36, terms and conditions data 38, card member agreement data 40, result data 42, etc. For example, the consumer input data 34 may include multiple data fields populated with data reflecting a name, a consumer key, a consumer identification, an account number, an address, a city, a state, a zip code, a country, a telephone number, an e-mail address, a social security number, a date of birth, the merchant's name, an identification, an order number, an authorization number, an authorization time, an authorization amount, a ship-to address, a bill-to address, a transaction amount, a consumer purchase demographic, a transaction date, a transaction type, a product identification, a service identification, shipping costs, delivery type, consumer type, a company identity, a merchant identity, previous transaction data, geographical data, credit account data, bankcard balance data, delinquency data, credit segment data, previous transaction data, time between transactions data, previous transaction amount, previous transaction approval status, previous transaction time stamp data, a response code, consumer payment method, consumer payment history, consumer account history, consumer credit account balance, income data, family data, employment data, relationship data, expense data, application data, acknowledgement data, selection data, choice data, or any combination thereof.

In another aspect of the present invention, and as illustrated in FIG. 3, during the transaction, the consumer 16 supplies certain consumer data 44 (such as input data 34) while engaged in certain portions or steps in the transaction process. For example, the consumer 16 may, during the course of the transaction, provide his or her name, address, e-mail, authorized billing amount, bill-to-address, ship-to-address, etc. Therefore, in connection with the present invention, when the data fields 24 are presented to the consumer 16 at the interactive interface 28, such as offer data 32, application data 36, etc., certain information has already been provided by the consumer 16 at the merchant 18 location.

Therefore, and as shown in operation in FIG. 3, the consumer 16 may be provided with one or even a variety of credit products 12, and after selecting the appropriate credit product 12, the application data 36 or application is presented to the consumer 16 at the interactive interface 28. Accordingly, as shown in the example of FIG. 3, the consumer 16 has selected credit product A, and the system 10 has presented the application or application data 36 to the consumer 16. However, various data fields 24, as discussed above, have been obtained from the consumer 16 during the transaction. Therefore, these data fields 24 may be pre-populated at the point of application, and would not require the consumer 16 to duplicate any data entry. In particular, in this embodiment, various consumer data 44 is taken and transferred from a consumer interaction page 46 that has already been completed by the consumer 16 with this consumer data 44. Accordingly, this consumer data 44 is placed in the appropriate portions and data fields 24 of the application. Of course, the consumer 16 may modify this consumer data 44 if desired, however the pre-population provides an extra convenience to the consumer 16 and facilitates a smoother transaction and credit product 12 acquisition process.

The consumer interaction page 46 during the transaction may take various forms. For example, the consumer interaction page 46 may be an application, a survey, a questionnaire, an acknowledgment, a form, a modifiable form, a template, etc. However, due to the locality of the presently-invented method and system 10, namely at the point-of-sale, this consumer data 44 is easily utilized and pre-populated where appropriate.

In operation, and as shown in FIG. 4 in schematic form, the consumer 16 and merchant 18 are engaged in a transaction. Next, one or more credit products 12 are offered to the consumer 16 at the point-of-sale of the merchant 18. The appropriate information and data, namely the appropriate data fields 24 of the credit issuer data set 20, is provided to the consumer 16. Next, offer input data 34 is obtained from the consumer 16, which is directed to the credit product 12 offer. If the consumer 16 accepts the offer, the system 10 next presents, to the consumer 16, terms and conditions data 38 and/or card member agreement data 40. Accordingly, responsive to this presentation, the consumer 16 provides additional input data 34, such as acknowledgment input data 34.

Prior to presentation of the terms and conditions data 38 and card member agreement data 40, and as discussed above, an application or application data 36 may be presented or provided to the consumer 16. Therefore, additional application input data 34 is received from the consumer 16. Accordingly, based upon the appropriate processes run at either the merchant 18 site, or more preferably the central system 30 (or even at the credit issuer 14 site), the application is approved or denied based upon the application input data 34. If approved, an account may be established and opened for the consumer 16 for the credit product 12 of the credit issuer 14. However, if denied, some denial data or appropriate indication is delivered or presented to the consumer 16. It is further envisioned that the central system 30 may determine consumer risk data or perform other risk analysis, verification, authentication, etc., based on the offer input data 34, the acknowledgment input data 34, the application input data 34, or any combination thereof.

Turning to FIG. 5, and in one preferred and non-limiting embodiment, the central database 22 is located or housed within the central system 30. In addition, multiple credit issuers 14 include individual and specified credit issuer data sets 20. For example, these individual credit issuer data sets 20 represent a subset of data including the data fields 24, which are populated with data reflecting the specified credit issuer 14 and/or credit product 12. In one embodiment, the credit issuer 14 is capable of configuring, programming, modifying and otherwise manipulating this subset of data, or specified individual credit issuer data set 20, for the credit issuer 14.

In another embodiment, the credit issuer 14 engages in the transmission of this subset of data or the credit issuer data set 20, in order to maintain absolute control over such data. Therefore, this subset may be equal to the credit issuer data 20 or be another set of data that is modifiable and requires a higher level of access by the credit issuer 14. Of course, any level of credit issuer 14 access to the central database 22 is envisioned, given the appropriate security measures.

In the embodiment of FIG. 5, the individual credit issuer data sets 20 are transmitted to the same or a duplicate central database 22 at the merchant 18 site over the network N. Accordingly, the merchant 18 is in communication with or maintains a merchant database 48, which is in communication with the central database 22. In operation, during the transaction, the subset of data or credit issuer data set 20 is accessible by and through the merchant database 48 for presentation to the consumer 16. In addition, the merchant database 48 may be maintained or updated on a specified basis, a periodic basis, a predetermined basis, a dynamic basis, etc. Accordingly, such a system allows multiple credit issuers 14 to provide multiple credit products 12 to the consumer 16 through the merchant 18 at the point-of-sale.

As seen in FIG. 6, the present invention is also directed to a system 10 for offering at least one credit product 12 by at least one credit issuer 14 to a consumer 16 at a point-of-sale between a merchant 18 and the consumer 16. This system 10 includes a storage mechanism 100, which includes the central database 22. One or more input mechanisms 102 are provided for transmitting, to the storage mechanism 100, the credit issuer data set 20, having the multiple data fields 24 therein. A processor mechanism 104 is included and used and configured or programmed to process data input, data requests, data manipulation, data transmission, etc. A merchant output mechanism 106 is used and configured or programmed to present, to the consumer 16 at the point-of-sale, the one or more data fields 24 of the credit issuer data set 20. In addition, as discussed above, the data fields 24 are populated with data directed to the credit product 12.

The input mechanism 102 may also be used on the merchant 18 side for transmitting a request, from the merchant 18, for the data fields 24 of the credit issuer data set 20. Of course, this assumes the embodiment where the central database 22 and storage mechanism 100 are at the central system 30, as opposed to at the location of or under the control of the merchant 18. In addition, the system 10 may include a communication mechanism 108 for transmitting, to the merchant 18, the data fields 24 and credit issuer data set 20 from the central database 22, which is responsive to the merchant 18 request. Of course it is further envisioned that the credit issuers 14 have an appropriate input mechanism 102 for providing their individualized subsets of data or individualized and specific credit issuer data sets 20 and/or data fields 24 to the central database 22 on the storage mechanism 100.

In this manner, the present invention provides a method and system 10 for offering one or more credit products 12 by one or more credit issuers 14 to a consumer 16 at a point-of-sale with a merchant 18. Accordingly, during the transaction process, appropriate data fields 24 from the credit issuer data set 20 is presented or provided to the consumer 16 at the point-of-sale, and these data fields 24 are timely, accurate, complete and verified by the respective credit issuers 14 for the credit product 12. In an electronic transaction, the consumer 16 does not need to leave, initiate direct communication with or be otherwise directed to a credit issuer 14 site or other third party location. Instead, the merchant 18 maintains control over the consumer 16, but also presents the most appropriate and accurate data fields 24 thereto. Therefore, the present invention provides a seamless and efficient credit transaction between a consumer 16 and a credit issuer 14 at the point-of-sale between the merchant 18 and the consumer 16. In addition, the present invention ensures that the data fields 24 and/or credit issuer data set 20 presented to the consumer 16 meets the approval of the credit issuers 14, who are ultimately in control of these data fields 24.

Although the invention has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred embodiments, it is to be understood that such detail is solely for that purpose and that the invention is not limited to the disclosed embodiments, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present invention contemplates that, to the extent possible, one or more features of any embodiment can be combined with one or more features of any other embodiment. 

1. (canceled)
 2. A system comprising: a non-transitory memory; and one or more hardware processors coupled with the non-transitory memory and configured to read instructions from the non-transitory memory to cause the system to perform operations comprising: displaying, by a marketplace entity via a graphical user interface, a first user interface element corresponding to one or more credit products associated with a first entity that is different than the marketplace entity; in response to detecting, by the marketplace entity, a selection by a user of the first user interface element corresponding to the one or more credit products associated with the first entity, transmitting, by the marketplace entity, a user data associated with the user to the first entity, wherein the transmitting causes the first entity to identify a first credit product of the one or more credit products to provide to the user; displaying, by the marketplace entity via the graphical user interface, a second user interface element corresponding to the first credit product; and in response to detecting, by the marketplace entity, a selection by the user of the second user interface element, causing, by the marketplace entity, a processing of a transaction of the user using the first credit product without redirecting the user away from the graphical user interface of the marketplace entity.
 3. The system of claim 2, wherein the operations further comprise providing a notification via the graphical user interface indicating that the first credit product has been used in processing the transaction.
 4. The system of claim 2, wherein the operations further comprise displaying, by the marketplace entity via the graphical user interface, a second user interface element corresponding to one or more credit products associated with second entity that is different than the first entity and the marketplace entity.
 5. The system of claim 2, wherein the causing the first entity to identify the first credit product of the one or more credit products to provide to the user is based on the first entity determining that the user is eligible for the first credit product based on user data received from the marketplace entity.
 6. The system of claim 2, wherein the operations further comprise displaying, by the marketplace entity via the graphical user interface, one or more data fields in association with the one or more credit products associated with the first entity, wherein the marketplace entity is in communication with the first entity to cause the one or more data fields populate one or more data in the one or more data fields.
 7. The system of claim 6, wherein the one or more data includes an interest rate data, a payment term data or a fee data.
 8. The system of claim 2, wherein the operations further comprise displaying, by the marketplace entity via the graphical user interface, one or more data fields in association with the one or more credit products associated with the first entity, wherein the one or more data fields prompt the user for one or more types of information.
 9. A method, comprising: displaying, by a marketplace entity via a graphical user interface, a first user interface element corresponding to one or more credit products associated with a first entity that is different than the marketplace entity; in response to detecting, by the marketplace entity, a selection by a user of the first user interface element corresponding to the one or more credit products associated with the first entity, transmitting, by the marketplace entity, a user data associated with the user to the first entity, wherein the transmitting causes the first entity to identify a first credit product of the one or more credit products to provide to the user; displaying, by the marketplace entity via the graphical user interface, a second user interface element corresponding to the first credit product; and in response to detecting, by the marketplace entity, a selection by the user of the second user interface element, causing, by the marketplace entity, a processing of a transaction of the user using the first credit product without redirecting the user away from the graphical user interface of the marketplace entity.
 10. The method of claim 9, further comprising providing a notification via the graphical user interface indicating that the first credit product has been used in processing the transaction.
 11. The method of claim 9, further comprising displaying, by the marketplace entity via the graphical user interface, a second user interface element corresponding to one or more credit products associated with second entity that is different than the first entity and the marketplace entity.
 12. The method of claim 9, wherein the causing the first entity to identify the first credit product of the one or more credit products to provide to the user is based on the first entity determining that the user is eligible for the first credit product based on user data received from the marketplace entity.
 13. The method of claim 9, further comprising displaying, by the marketplace entity via the graphical user interface, one or more data fields in association with the one or more credit products associated with the first entity, wherein the marketplace entity is in communication with the first entity to cause the one or more data fields populate one or more data in the one or more data fields.
 14. The method of claim 13, wherein the one or more data includes an interest rate data, a payment term data or a fee data.
 15. The method of claim 9, further comprising displaying, by the marketplace entity via the graphical user interface, one or more data fields in association with the one or more credit products associated with the first entity, wherein the one or more data fields prompt the user for one or more types of information.
 16. A non-transitory machine-readable medium stored thereon machine-readable instructions executable to cause a machine to perform operations comprising: displaying, by a marketplace entity via a graphical user interface, a first user interface element corresponding to one or more credit products associated with a first entity that is different than the marketplace entity; in response to detecting, by the marketplace entity, a selection by a user of the first user interface element corresponding to the one or more credit products associated with the first entity, transmitting, by the marketplace entity, a user data associated with the user to the first entity, wherein the transmitting causes the first entity to identify a first credit product of the one or more credit products to provide to the user; displaying, by the marketplace entity via the graphical user interface, a second user interface element corresponding to the first credit product; and in response to detecting, by the marketplace entity, a selection by the user of the second user interface element, causing, by the marketplace entity, a processing of a transaction of the user using the first credit product without redirecting the user away from the graphical user interface of the marketplace entity.
 17. The non-transitory machine-readable medium of claim 16, wherein the operations further comprise providing a notification via the graphical user interface indicating that the first credit product has been used in processing the transaction.
 18. The non-transitory machine-readable medium of claim 16, wherein the operations further comprise displaying, by the marketplace entity via the graphical user interface, a second user interface element corresponding to one or more credit products associated with second entity that is different than the first entity and the marketplace entity.
 19. The non-transitory machine-readable medium of claim 16, wherein the causing the first entity to identify the first credit product of the one or more credit products to provide to the user is based on the first entity determining that the user is eligible for the first credit product based on user data received from the marketplace entity.
 20. The non-transitory machine-readable medium of claim 16, wherein the operations further comprise displaying, by the marketplace entity via the graphical user interface, one or more data fields in association with the one or more credit products associated with the first entity, wherein the marketplace entity is in communication with the first entity to cause the one or more data fields populate one or more data in the one or more data fields.
 21. The non-transitory machine-readable medium of claim 20, wherein the one or more data includes an interest rate data, a payment term data or a fee data. 